Skip to content

[FLINK-36334][tests] Enable Remove the Disable markers from the tests in the various TypeSerializerUpgradeTestBase subclasses in flink-table-api-scala module#28549

Open
SteveStevenpoor wants to merge 1 commit into
apache:masterfrom
SteveStevenpoor:FLINK-36334

Conversation

@SteveStevenpoor

Copy link
Copy Markdown
Contributor

What is the purpose of the change

This pull request enables the last remaining subclass of TypeSerializerUpgradeTestBase. All the other subclasses were enabled in #28506 .

Brief change log

  • Regenerated test data for release-2.0, 2.1 and 2.2 using ListBuffer instead of MutableList
  • Fixed naming for consistency

Verifying this change

This change simply enables TraversableSerializerUpgradeTest.

Does this pull request potentially affect one of the following parts:

  • Dependencies (does it add or upgrade a dependency): no
  • The public API, i.e., is any changed class annotated with @Public(Evolving): no
  • The serializers: no
  • The runtime per-record code paths (performance sensitive): no
  • Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
  • The S3 file system connector: no

Documentation

  • Does this pull request introduce a new feature? no
  • If yes, how is the feature documented? not applicable

@flinkbot

flinkbot commented Jun 26, 2026

Copy link
Copy Markdown
Collaborator

CI report:

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot run azure re-run the last Azure build

@SteveStevenpoor

Copy link
Copy Markdown
Contributor Author

@snuyanzin 36334 is ready. I patched previous releases just to generate proper test files. Now the test runs just fine. Next I will generate test files for release-2.3 and change most_recently_published_version to v2_3

@snuyanzin

Copy link
Copy Markdown
Contributor

Next I will generate test files for release-2.3 and change most_recently_published_version to v2_3

this is the task that should be done by release managers after release published, so better to communicate with them first about it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants